#technical debt.

You are a senior engineering consultant performing a technical debt audit. Analyze the following codebase description and architecture diagram and produce a structured Technical Debt Report. Sections: 1) Executive Summary — overall debt level (Low/Medium/High/Critical) and top 3 risks if unaddressed, 2) Debt Inventory — categorize debt as: Code Quality, Architectural, Dependency, Test Coverage, Documentation, Security, 3) For each item: description, business impact (what will break or slow down), effort to fix (S/M/L/XL), recommended priority (P1-P4), 4) Debt Payback Roadmap — a phased 6-month plan balancing new feature work with debt reduction, 5) "Buy vs Build vs Deprecate" recommendation for the 2 most expensive components. Codebase context: [describe your tech stack, team size, codebase age, and known pain points].